Security, monitoring and automation controller access and use of legacy security control panel information

ABSTRACT

A system, method and apparatus for controller functionality for each of security, monitoring and automation, as well as a bidirectional Internet gateway, is provided. Such functionality is provided by virtue of a configurable architecture that enables a user to adapt the system for the user&#39;s specific needs. In addition, functionality for gathering configuration information from a previously-installed security system and using that information in a subsequent takeover of that security system is provided.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of United States (U.S.) patent application Ser. No. 12/732,879, filed Mar. 26, 2010, which is a continuation-in-part of U.S. patent application Ser. No. 11/712,175, entitled “Method and System for Coupling an Alarm System to an External Network”, filed Feb. 28, 2007, and naming Alan Wade Cohn, Ronald E. Battles, David Proft, and Scott William Shumate as inventors. This application also claims priority from Provisional Patent Application Ser. No. 61/174,366, entitled “Remote Security Station,” filed Apr. 30, 2009, and naming Alan Wade Cohn as inventor. This provisional patent application is incorporated herein by reference in its entirety and for all purposes.

FIELD OF THE INVENTION

Embodiments of the present invention relate generally to the field of home security monitoring and automation, and specifically to accessing sensor configuration information of a legacy security control panel and taking over of the legacy security control panel by a user-configurable controller for security, monitoring and automation.

BACKGROUND OF THE INVENTION

Residential electronics and control standards provide an opportunity for a variety of options for securing, monitoring, and automating residences. Wireless protocols for transmission of security information permit placement of a multitude of security sensors throughout a residence without a need for running wires back to a central control panel. Inexpensive wireless cameras also allow for placement of cameras throughout a residence to enable easy monitoring of the residence. A variety of home automation control protocols have also been developed to allow for centralized remote control of lights, appliances, and environmental apparatuses (e.g., thermostats). Traditionally, each of these security, monitoring and automation protocols require separate programming, control and monitoring stations. To the extent that home automation and monitoring systems have been coupled to home security systems, such coupling has involved including the automation and monitoring systems as slaves to the existing home security system. This limits the flexibility and versatility of the automation and monitoring systems and ties such systems to proprietary architectures.

A security system alerts occupants of a dwelling and emergency authorities of a violation of premises secured by the system. A typical legacy security system includes a controller connected by wireless or wired connections to sensors deployed at various locations throughout the secured dwelling. In a home, sensors are usually deployed in doorways, windows, and other points of entry. Motion sensors can also be placed strategically within the home to detect unauthorized movement, while smoke and heat sensors can detect the presence of fire.

A home monitoring system provides an ability to monitor a status of a home so that a user can be made aware of any monitored state changes. For example, when a sensor is tripped, real-time alerts and associated data such as video or photo clips can be sent to the user (e.g., to a network-connected computer or to a mobile device).

A home automation system enables automation and remote control of lifestyle conveniences such as lighting, heating, cooling, and appliances. Typically these various lifestyle conveniences are coupled to a controller via wireless or wired communications protocols. A central device is then used to program the various lifestyle conveniences.

Rather than having multiple devices to control each of the security, monitoring and automation environments, it is desirable to have a centralized controller capable of operating in each environment, thereby reducing the equipment needed in a dwelling. It is further desirable for such a controller to function as a gateway for external network access so that a user can control or monitor devices in locations remote from the dwelling.

Many dwellings have a legacy security system installed with a variety of security sensors wired to the legacy system or otherwise communicating with the legacy system (e.g., using RF sensors). It is thus also desirable for a security, monitoring and automation controller to utilize those pre-existing sensors by taking over the security function of the legacy system, monitoring the legacy sensors for state changes and reporting those state changes to a user or to emergency authorities. It is also desirable for such functionality to be provided using an activation and provisioning work flow that allows for installers with minimal training to perform such activation and provisioning.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a single platform that provides controller functionality for each of security, monitoring and automation, as well as providing a capacity to function as a bidirectional Internet gateway. Embodiments of the present invention provide such functionality by virtue of a configurable architecture that enables a user to adapt the system for the user's specific needs. Embodiments of the present invention further provide for gathering information from a legacy security system and subsequent takeover of that system.

In one embodiment of the present invention, a security, monitoring and automation (SMA) controller is coupled to an unarmed legacy controller of a previously-installed security system. The SMA controller then receives sensor configuration information from the legacy controller and stores that information in the SMA controller. When a sensor trip signal is received from the legacy controller, the SMA controller transmits either an alarm signal message or a sensor trip signal message to a remote computer, depending upon whether the SMA controller is armed or not, respectively.

In one aspect of the above embodiment, the SMA controller is coupled to the legacy controller by a keypad bus of the legacy controller. This coupling can be either a hardwired connection between the SMA controller and the keypad bus, or by using a wireless transceiver coupled to the keypad bus that, in turn, communicates with the SMA controller. In a further aspect of the above embodiment, the SMA controller can determine a communications protocol of the keypad bus by receiving and interpreting messages transmitted by the legacy controller on the keypad bus. The SMA controller can then transmit messages to the legacy controller using the determined communications protocol, including a message to request the sensor and zone configuration information from the legacy controller.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings.

FIG. 1 is a simplified block diagram illustrating an architecture including a set of logical domains and functional entities within which embodiments of the present invention interact.

FIG. 2 is a simplified block diagram illustrating a hardware architecture of an SMA controller, according to one embodiment of the present invention.

FIG. 3 is a simplified block diagram illustrating a logical stacking of an SMA controller's firmware architecture, usable with embodiments of the present invention.

FIG. 4 is an illustration of an example user interface for an SMA controller 120, according to an embodiment of the present invention.

FIG. 5 is a simplified block diagram illustrating elements of a legacy security system.

FIG. 6A is a simplified block diagram of components of a legacy security system coupled to an SMA controller, in accord with one embodiment of the present invention.

FIG. 6B is a simplified block diagram illustrating components of an alternative coupling between a legacy security system and an SMA controller, in accord with another embodiment of the present invention.

FIG. 7 is a simplified flow diagram illustrating an example of a process by which an SMA controller can access and store configuration information from a legacy security system, in accord with embodiments of the present invention.

FIG. 8 is a simplified flow diagram illustrating a process performed in response to a legacy sensor state change, in accord with embodiments of the present invention.

FIG. 9 illustrates a block diagram of a computer system suitable for implementing aspects of the present invention.

FIG. 10 is a block diagram illustrates a network architecture suitable for implementing aspects of the present invention.

DETAILED DESCRIPTION

Embodiments of the present invention provide a single platform that provides controller functionality for each of security, monitoring and automation, as well as providing a capacity to function as a bidirectional Internet gateway. Embodiments of the present invention provide such functionality by virtue of a configurable architecture that enables a user to adapt the system for the user's specific needs. Embodiments of the present invention provide for gathering configuration information from a previously-installed security system and using that information in a subsequent takeover of that security system.

Architectural Overview

Embodiments of the configurable security, monitoring and automation (SMA) controller of the present invention provide not only for communicating with and interpreting signals from sensors and devices within a dwelling, but also for accessing and monitoring those sensors and devices from locations remote to the dwelling. Embodiments of the SMA controller provide such capability through linkages to external servers via access networks such as the Internet, provider network, or a cellular network. The external servers provide a portal environment through which a user can, for example, monitor the state of sensors coupled, directly or indirectly, to the SMA controller in real-time, configure the controller, and provide controlling information to the SMA controller. The servers can further automatically provide information to a user via remote devices such as mobile phones, computers, and pagers. The servers further provide a connection to a traditional security central station, which can then contact authorities in the event of an alarm condition being detected by the SMA controller in the dwelling.

FIG. 1 is a simplified block diagram illustrating an architecture including a set of logical domains and functional entities within which embodiments of the present invention interact. A home domain 110 includes an embodiment of the SMA controller 120. The home domain is coupled via an access domain 150 to an operator domain 160 that includes various servers. The servers are in turn coupled to a central station 190 and to various remote user communication options.

The home domain refers to a collection of security, monitoring and automation entities within a dwelling or other location having SMA devices. SMA controller 120 is a device that provides an end-user SMA interface to the various SMA entities (e.g., radio-frequency sensors) within home domain 110. SMA controller 120 further acts as a gateway interface between home domain 110 and operator domain 160. SMA controller 120 provides such gateway access to operator domain 160 via a network router 125. Network router 125 can be coupled to SMA controller 120 and to home network devices such as home computer 127 via either hard wired or wireless connections (e.g., WiFi, tethered Ethernet, and power-line network). A network router 125 coupled to a broadband modem (e.g., a cable modem or DSL modem) serves as one link to networks in access domain 150.

SMA devices within home domain 110 can include a variety of RF or wireless sensors 130 whose signals are received and interpreted by SMA controller 120. RF sensors 130 can include, for example, door or window sensors, motion detectors, smoke detectors, glass break detectors, inertial detectors, water detectors, carbon dioxide detectors, and key fob devices. SMA controller 120 can be configured to react to a change in state of any of these detectors.

In addition to acting and reacting to changes in state of RF sensors 130, SMA controller 120 also can be coupled to a previously-installed legacy security system 135. SMA controller 120 can automatically gather configuration information from legacy security system 135 and maintain that configuration information in memory to interpret signals received from sensors coupled to the legacy security system. SMA controller 120 then uses that configuration information to control the legacy security system by interpreting signals generated by a legacy security system controller in response to state changes from sensors coupled to the legacy security system and reacting in a user-configured manner. SMA controller 120, for example, will provide alarm or sensor state information from legacy security system 135 to servers in operator domain 160 that may ultimately inform central station 190 to take appropriate action. In this manner, SMA controller 120 replaces alarm communication paths originally used by the legacy security system.

SMA controller 120 can also be coupled to one or more monitoring devices 140. Monitoring devices 140 can include, for example, still and video cameras that provide images that are viewable on a screen of SMA controller 120 or a remotely connected device. Monitoring devices 140 can be coupled to SMA controller 120 either wirelessly (e.g., WiFi via router 125) or other connections.

Home automation devices 145 (e.g., home area network devices having an automation interface) can also be coupled to and controlled by SMA controller 120. SMA controller 120 can be configured to interact with a variety of home automation protocols, such as, for example, Z-Wave and ZigBee.

Embodiments of SMA controller 120 can be configured to communicate with a variety of RF or wireless sensors and are not limited to the RF sensors, monitoring devices and home automation devices discussed above. A person of ordinary skill in the art will appreciate that embodiments of the present invention are not limited to or by the above-discussed devices and sensors, and can be applied to other areas and devices.

Embodiments of SMA controller 120 can be used to configure and control home security devices (e.g., 130 and 135), monitoring devices 140 and automation devices 145, either directly or by providing a gateway to remote control via servers in operator domain 160. SMA controller 120 communicates with servers residing in operator domain 160 via networks in access domain 150. Broadband communication can be provided by coupling SMA controller 120 with a network router 125, which in turn is coupled to a wide area network 152, such as a provider network or the Internet, via an appropriate broadband modem. The router can be coupled to the wide area network through cable broadband, DSL, and the like. Wide area network 152, in turn, is coupled to servers in operator domain 160 via an appropriate series of routers and firewalls (not shown).

SMA controller 120 can also include additional mechanisms to provide a communication with the operator domain. For example, SMA controller 120 can be configured with a cellular network transceiver that permits communication with a cellular network 154. In turn, cellular network 154 can provide access via routers and firewalls to servers in operator domain 160. Embodiments of SMA controller 120 are not limited to providing gateway functionality via cellular and dwelling-based routers and modems. For example, SMA controller 120 can be configured with other network protocol controllers such as WiMAX satellite-based broadband, direct telephone coupling, and the like.

Operator domain 160 refers to a logical collection of SMA servers and other operator systems in an operator's network that provide end-user interfaces, such as portals accessible to subscribers of the SMA service, that can configure, manage and control SMA elements within home domain 110. Servers in operator domain 160 can be maintained by a provider (operator) of subscriber-based services for SMA operations. Examples of providers include cable providers, telecommunications providers, and the like. A production server architecture in operator domain 160 can support SMA systems in millions of home domains 110.

Individual server architectures can be of a variety of types, and in one embodiment, the server architecture is a tiered Java2 Enterprise Edition (J2EE) service oriented architecture. Such a tiered service oriented architecture can include an interface tier, a service tier, and a data access logic tier. The interface tier can provide entry points from outside the server processes, including, for example, browser web applications, mobile web applications, web services, HTML, XHTML, SOAP, and the like. A service tier can provide a variety of selectable functionality passed along by the operator to the end user. Service tiers can relate to end user subscription levels offered by the operator (e.g., payment tiers corresponding to “gold” level service, “silver” level service and “bronze” level service). Finally the data access logic tier provides access to various sources of data including database servers.

FIG. 1 illustrates an example set of servers that can be provided in operator domain 160. Servers 165 can support all non-alarm and alarm events, heartbeat, and command traffic between the various servers and SMA controllers 120. Servers 165 can also manage end-user electronic mail and SMS notification, as well as integration with provider billing, provisioning, inventory, tech support systems, and the like.

A portal server 170 can provide various user interface applications, including, for example, a subscriber portal, a mobile portal, and a management portal. A subscriber portal is an end-user accessible application that permits an end-user to access a corresponding SMA controller remotely via standard web-based applications. Using such a subscriber portal can provide access to the same SMA functions that an interface directly coupled to the SMA controller would provide, plus additional functions such as alert and contact management, historical data, widget and camera management, account management, and the like. A mobile portal can provide all or part of the access available to an end-user via the subscriber portal. A mobile portal can be limited, however, to capabilities of an accessing mobile device (e.g., touch screen or non-touch screen cellular phones). A management portal provides an operator representative access to support and manage SMA controllers in home domains 110 and corresponding user accounts via a web-based application. The management portal can provide tiers of management support so that levels of access to user information can be restricted based on authorization of a particular employee.

Telephony server 180 can process and send information related to alarm events received from SMA controllers 120 to alarm receivers at central monitoring station 190. A server 165 that processes the alarm event makes a request to telephony server 180 to dial the central station's receiver and send corresponding contact information. Telephony server 180 can communicate with a plurality of central stations 190. Server 165 can determine a correct central station to contact based upon user account settings associated with the transmitting SMA controller. Thus, alarms can be routed to different central stations based upon user accounts. Further, accounts can be transferred from one central station to another by modifying user account information. Telephony server 180 can communicate with alarm receivers at central station 190 using, for example, a security industry standard contact identification protocol (e.g., dual-tone multi-frequency [DTMF]) and broadband protocols.

A backup server 175 can be provided to guarantee that an alarm path is available in an event that one or more servers 165 become unavailable or inaccessible. A backup server 175 can be co-located to the physical location of servers 165 to address scenarios in which one or more of the servers fail. Alternatively, a backup server 175 can be placed in a location remote from servers 165 in order to address situations in which a network failure or a power failure causes one or more of servers 165 to become unavailable. SMA controllers 120 can be configured to transmit alarm events to a backup server 175 if the SMA controller cannot successfully send such events to servers 165.

A database server 185 provides storage of all configuration and user information accessible to other servers within operator domain 160. Selection of a type of database provided by database server 185 can be dependent upon a variety of criteria, including, for example, scalability and availability of data. One embodiment of the present invention uses database services provided by an ORACLE database.

A server 165 in operator domain 160 provides a variety of functionality. Logically, a server 165 can be divided into the following functional modules: a broadband communication module, a cellular communication module, a notification module, a telephony communication module, and an integration module.

The broadband communication module manages broadband connections and message traffic from a plurality of SMA controllers 110 coupled to server 165. Embodiments of the present invention provide for the broadband channel to be a primary communication channel between an SMA controller 120 and servers 165. The broadband communication module handles a variety of communication, including, for example, all non-alarm and alarm events, broadband heartbeat, and command of traffic between server 165 and SMA controller 120 over the broadband channel. Embodiments of the present invention provide for an always-on persistent TCP socket connection to be maintained between each SMA controller and server 165. A variety of protocols can be used for communications between server 165 and SMA controller 120 (e.g., XML over TCP, and the like). Such communication can be secured using standard transport layer security (TLS) technologies. Through the use of an always-on socket connection, servers 165 can provide near real-time communication between the server and an SMA controller 120. For example, if a user has a subscriber portal active and a zone is tripped within home domain 110, a zone fault will be reflected in near real-time on the subscriber portal user interface.

The cellular communication module manages cellular connections and message traffic from SMA controllers 120 to a server 165. Embodiments of the present invention use the cellular channel as a backup communication channel to the broadband channel. Thus, if a broadband channel becomes unavailable, communication between an SMA controller and a server switches to the cellular channel. At this time, the cellular communication module on the server handles all non-alarm and alarm events, and command traffic from an SMA controller. When a broadband channel is active, heartbeat messages can be sent periodically on the cellular channel in order to monitor the cellular channel. When a cellular protocol communication stack is being used, a TCP socket connection can be established between the SMA controller and server to ensure reliable message delivery for critical messages (e.g., alarm events and commands). Once critical messages have been exchanged, the TCP connection can be shut down thereby reducing cellular communication costs. As with broadband communication, XMPP can be the messaging protocol used for such communications. Similarly, such communication can be secured using TLS and SASL authentication protocols. Non-critical messages between an SMA controller and a server can be sent using UDP. A compressed binary protocol can be used as a messaging protocol for such communications in order to minimize cellular costs for such message traffic. Such messages can be secured using an encryption algorithm, such as the tiny encryption algorithm (TEA). Cellular communication can be established over two network segments: the GSM service provider's network that provides a path between an SMA controller and a cellular access point, and a VPN tunnel between the access point and an operator domain data center.

A notification module of server 165 determines if and how a user should be notified of events generated by their corresponding SMA controller 120. A user can specify who to notify of particular events or event types and how to notify the user (e.g., telephone call, electronic mail, text message, page, and the like), and this information is stored by a database server 185. When events such as alarm or non-alarm events are received by a server 165, those events can be past asynchronously to the notification module, which determines if, who and how to send those notifications based upon the user's configuration.

The telephony communication module provides communication between a server 165 and telephony server 180. When a server 165 receives and performs initial processing of alarm events, the telephony communication module forwards those events to a telephony server 180 which in turn communicates with a central station 190, as discussed above.

The integration module provides infrastructure and interfaces to integrate a server 165 with operator business systems, such as, for example, billing, provisioning, inventory, tech support, and the like. An integration module can provide a web services interface for upstream integration that operator business systems can call to perform operations like creating and updating accounts and querying information stored in a database served by database server 185. An integration module can also provide an event-driven framework for downstream integration to inform operator business systems of events within the SMA system.

SMA Controller Architecture

FIG. 2 is a simplified block diagram illustrating a hardware architecture of an SMA controller, according to one embodiment of the present invention. A processor 210 is coupled to a plurality of communications transceivers, interface modules, memory modules, and user interface modules. Processor 210, executing firmware discussed below, performs various tasks related to interpretation of alarm and non-alarm signals received by SMA controller 120, interpreting reactions to those signals in light of configuration information either received from a server (e.g., server 165) or entered into an interface provided by SMA controller 120 (e.g., a touch screen 220). Embodiments of the present invention can use a variety of processors, for example, an ARM core processor such as a FREESCALE i.MX35 multimedia applications processor.

SMA controller 120 can provide for user input and display via a touch screen 220 coupled to processor 210. Processor 210 can also provide audio feedback to a user via use of an audio processor 225. Audio processor 225 can, in turn, be coupled to a speaker that provides sound in home domain 110. SMA controller 120 can be configured to provide a variety of sounds for different events detected by sensors associated with the SMA controller. Such sounds can be configured by a user so as to distinguish between alarm and non-alarm events.

As discussed above, an SMA controller 120 can communicate with a server 165 using different network access means. Processor 210 can provide broadband access to a router (e.g., router 125) via an Ethernet broadband connection PHY 130 or via a WiFi transceiver 235. The router can then be coupled to or be incorporated within an appropriate broadband modem. Cellular network connectivity can be provided by a cellular transceiver 240 that is coupled to processor 210. SMA controller 120 can be configured with a set of rules that govern when processor 210 will switch between a broadband connection and a cellular connection to operator domain 160.

In order to communicate with the various sensors and devices within home domain 110, processor 210 can be coupled to one or more transceiver modules via, for example, a serial peripheral interface such as a SPI bus 250. Such transceiver modules permit communication with sensors of a variety of protocols in a configurable manner. Embodiments of the present invention can use a transceiver to communicate with a variety of RF sensors 130 using a variety of communication protocols. Similarly, home automation transceivers (e.g., home area network devices having an automation interface) that communicate using, for example, Z-Wave or ZigBee protocols can be coupled to processor 210 via SPI 250. If SMA controller 120 is coupled to a legacy security system 135, then a module permitting direct coupling to the legacy security system can be coupled to processor 210 via SPI 250 (e.g., a module to interface with a keypad bus off the legacy security system). Alternatively, SMA controller 120 can be RF coupled to a legacy security system 135 using, for example, a ZigBee transceiver module to communicate with a ZigBee transceiver coupled to a controller of the legacy security system. Other protocols can be provided for via such plug-in modules including, for example, digital enhanced cordless communication devices (DECT). In this manner, an SMA controller 120 can be configured to provide for control of a variety of devices and protocols known both today and in the future. In addition, processor 210 can be coupled to other types of devices (e.g., transceivers or computers) via a universal serial bus (USB) interface 255.

In order to locally store configuration information for SMA controller 120, a memory 260 is coupled to processor 210. Additional memory can be coupled to processor 210 via, for example, a secure digital interface 265. A power supply 270 is also coupled to processor 210 and to other devices within SMA controller 120 via, for example, a power management controller module.

SMA controller 120 is configured to be a customer premises equipment device that works in conjunction with server counterparts in operator domain 160 in order to perform functions required for security monitoring and automation. Embodiments of SMA controller 120 provide a touch screen interface (e.g., 220) into all the SMA features. Via the various modules coupled to processor 210, the SMA controller bridges the sensor network, the control network, and security panel network to broadband and cellular networks. SMA controller 120 further uses the protocols discussed above to carry the alarm and activity events to servers in the operator domain for processing. These connections also carry configuration information, provisioning commands, management and reporting information, security authentication, and any real-time media such as video or audio.

FIG. 3 is a simplified block diagram illustrating a logical stacking of an SMA controller's firmware architecture, usable with embodiments of the present invention. Since SMA controller 120 provides security functionality for home domain 110, the SMA controller should be a highly available system. High availability suggests that the SMA controller be ready to serve an end-user at all times, both when a user is interacting with the SMA controller through a user interface and when alarms and other non-critical system events occur, regardless of whether a system component has failed. In order to provide such high availability, SMA controller 120 runs a micro-kernel operating system 310. An example of a micro-kernel operating system usable by embodiments of the present invention is a QNX real-time operating system. Under such a micro-kernel operating system, drivers, applications, protocol stacks and file systems run outside the operating system kernel in memory-protected user space. Such a micro-kernel operating system can provide fault resilience through features such as critical process monitoring and adaptive partitioning. As a result, components can fail, including low-level drivers, and automatically restart without affecting other components or the kernel and without requiring a reboot of the system. A critical process monitoring feature can automatically restart failed components because those components function in the user space. An adaptive partitioning feature of the micro kernel operating system provides guarantees of CPU resources for designated components, thereby preventing a component from consuming all CPU resources to the detriment of other system components.

A core layer 320 of the firmware architecture provides service/event library and client API library components. A client API library can register managers and drivers to handle events and to tell other managers or drivers to perform some action. The service/event library maintains lists of listeners for events that each manager or driver detects and distributes according to one of the lists.

Driver layer 330 interacts with hardware peripherals of SMA controller 120. For example, drivers can be provided for touch screen 220, broadband connection 230, WiFi transceiver 235, cellular transceiver 240, USB interface 255, SD interface 265, audio processor 225, and the various modules coupled to processor 210 via SPI interface 250. Manager layer 340 provides business and control logic used by the other layers. Managers can be provided for alarm activities, security protocols, keypad functionality, communications functionality, audio functionality, and the like.

Keypad user interface layer 350 drives the touch screen user interface of SMA controller 120. An example of the touch screen user interface consists of a header and a footer, widget icons and underlying widget user interfaces. Keypad user interface layer 350 drives these user interface elements by providing, for example, management of what the system Arm/Disarm interface button says and battery charge information, widget icon placement in the user face area between the header and footer, and interacting with widget engine layer 360 to display underlying widget user interface when a widget icon is selected.

In embodiments of the present invention, typical SMA controller functions are represented in the touch screen user interface as widgets (or active icons). Widgets provide access to the various security monitoring and automation control functions of SMA controller 120 as well as providing support for multi-media functionality through widgets that provide, for example, news, sports, weather and digital picture frame functionality. A main user interface screen can provide a set of icons, each of which represents a widget. Selection of a widget icon can then launch the widget. Widget engine layer 360 includes, for example, widget engines for native, HTML and FLASH-based widgets. Widget engines are responsible for displaying particular widgets on the screen. For example, if a widget is developed in HTML, selection of such a widget will cause the HTML widget engine to display the selected widget or touch screen 220. Information related to the various widgets is provided in widget layer 370.

FIG. 4 is an illustration of an example user interface for an SMA controller 120, according to an embodiment of the present invention. The illustrated user interface provides a set of widget icons 410 that provide access to functionality of SMA controller 120. As illustrated, widgets are provided to access security functionality, camera images, thermostat control, lighting control, and other settings of the SMA controller. Additional widgets are provided to access network-based information such as weather, news, traffic, and digital picture frame functionality. A header 420 provides access to an Arm/Disarm button 425 that allows for arming the security system or disarming it. Additional information can be provided in the header, such as, for example, network status messages. A footer 430 can provide additional status information such as time and date, as displayed.

A user can select widgets corresponding to desired functionality. Embodiments of the present invention provide for access to widgets via portal server 170. A provider of operator domain 160 can determine functionality accessible to users, either for all users or based upon tiers of users (e.g., subscription levels associated with payment levels). A user can then select from the set of accessible widgets and the selected widgets will be distributed and displayed on the user interface of SMA controller 120. Configurability of SMA controller 120 is also driven by user determined actions and reactions to sensor stimulus.

Coupling an SMA Controller to a Legacy Security System

FIG. 5 is a simplified block diagram illustrating elements of a legacy security system 500. Legacy security system 500 includes a controller unit 510. Controller unit 510 includes an alarm processor 520, which is coupled to sensors 530(1)-(N). Sensors 530(1)-(N) can be installed at various points of entry for a building to detect when such a point of entry is reached, and can also include, for example, motion, smoke, and fire detectors. Servers 530(1)-(N) can be hard wired to controller unit 510 or be RF coupled to the controller unit. Alarm processor 520 can be configured with zones each of which can include one or more sensors. Alarm processor 520 is further coupled to a telephone line interface 540. In the event of a triggering of one of sensors 530(1)-(N), alarm processor 520 can instruct telephone line interface 540 to dial a call through public switched telephone network (PSTN) 550 to a central monitoring service system 560. Alarm processor 520 can then send data through the connection to the central monitoring service system, providing information related to the type of security breach (e.g., identification of zone, fire or intrusion alarm, etc.).

Alarm processor 520 is also coupled to a keypad 570. Keypad 570 allows a user to control the alarm system by performing tasks such as arming and disarming the alarm system, activating an alarm sequence to activate an audible alarm and call to the central monitoring service system, sending a silent distress signal to the central monitoring service system, and programming and configuring alarm system 500. Keypad 570 includes a keypad processor 575, which is coupled to keys 580 through which the user can enter commands. Keypad 570 can also include, for example, visual indicators of the status of the alarm system such as LEDs or a display, which are coupled to the keypad processor.

Alarm processor 520 is coupled to keypad processor 575 through a keypad bus 590. Keypad bus 590 provides communication between the alarm processor and keypad processor using, for example, a serial digital protocol transmitted and received by the processors. One or more keypads can be connected to the alarm processor via the keypad bus.

Through the use of the keypad bus serial digital protocol, the alarm processor can provide to the keypad information such as whether the alarm is armed or disarmed, and whether zones are tripped or not. The keypad processor can provide arming codes and other control information to the alarm processor.

FIG. 6A is a simplified block diagram of components of a legacy security system coupled to an SMA controller 120 in accord with one embodiment of the present invention. As discussed above, controller unit 510 includes an alarm processor 520 that is coupled to sensors 530(1)-(N). Alarm processor 520 is coupled via keypad bus 590 to keypad processor 575 within keypad 570. SMA controller 120 provides a processor 210 that is coupled to alarm processor 520 and keypad processor 575 via keypad bus 590. As discussed above, this coupling can be performed using a module coupled to SMA controller processor 210 via SPI interface 250 (e.g., a keypad bus connect module 610). Through this coupling, SMA controller 120 can exchange data with alarm processor 520 using an appropriate serial digital protocol.

SMA controller 120 can be configured to automatically determine the serial digital protocol being used in communications on the keypad bus as part of a configuration process of the SMA controller subsequent to keypad bus coupling. This automatic determination of the appropriate serial digital protocol can be performed, for example, passively by analyzing communications between the alarm processor and the keypad processor, or actively by transmitting packets of varying serial digital protocols onto the keypad bus until an expected response is received from the alarm controller.

FIG. 6B is a simplified block diagram illustrating components of an alternative coupling between a legacy security system and an SMA controller 120, in accord with another embodiment of the present invention. As in FIG. 6A, alarm processor 520 is coupled via keypad bus 590 to keypad processor 575 within keypad 570. An RF keypad bus interface 620 is coupled to keypad bus 590. Through such a coupling, RF keypad bus interface 620 can receive signals transmitted by alarm processor 520 on keypad bus 590 and transmit those signals to SMA controller 120. SMA controller 120 can receive those RF signals using an RF interface 630 coupled to processor 210 via, for example, SPI interface 250. SMA controller 120 can also provide controlling signals to alarm processor 520 via the RF interfaces 620 and 630. RF interfaces 620 and 630 can communicate using a variety of RF protocols including, for example, ZigBee. As with the configuration illustrated in FIG. 6A, SMA controller 120 can be configured to automatically determine the type of serial digital protocol used on the keypad bus during configuration of the SMA controller.

FIGS. 6A and 6B provide examples of configurations of communicative coupling of an SMA controller to an alarm processor. Embodiments of the present invention are not limited to the illustrated communicative coupling shown in those figures.

It should be noted that in both configurations illustrated in FIGS. 6A and 6B, alarm controller 510 is decoupled from PSTN 550. Once SMA controller 120 is configured to receive and interpret signals from alarm controller 510 (as discussed more fully below), the SMA controller monitors the state of sensors 530 and takes over reporting change of state and alarm events for the sensors coupled to the legacy security system, as well as those sensors coupled directly to the SMA controller.

Configuring an SMA Controller Coupled to a Legacy Security System

In accord with embodiments of the present invention, SMA controller 120 can be configured by a user in order to provide desired functionality in home domain 110. In addition to the hardware-configurable options discussed above (e.g., modules coupled to SPI interface 250), SMA controller 120 provides for additional configuration through the use of software and/or firmware. For example, SMA controller 120 can be configured to receive signals from a variety of security sensors (e.g., RF sensors 130) and to associate those sensors with the physical environment of home domain 110 (e.g., through the use of defined zones). In addition, SMA controller 120 can be configured to receive still and video information from one or more cameras, provide a variety of programs and utilities to a user, and is configurable to communicate with a variety of home automation devices.

As described above, SMA controller 120 can also be coupled to a legacy security system controller unit 510. Through such a coupling, SMA controller 120 can receive information about state changes of security sensors coupled to legacy security system controller unit 510 (e.g., sensors 530(1)-(N)), as communicated by alarm processor 520 over keypad bus 590. In order to properly interpret source and potential impact of those state changes, SMA controller 120 needs to be provided with configuration information programmed into legacy security system 510. SMA controller 120 can access such configuration information automatically by transmitting signals in an appropriate serial digital protocol on the keypad bus to cause alarm processor 520 to provide the configuration information to the SMA controller.

FIG. 7 is a simplified flow diagram illustrating an example of a process by which an SMA controller can access and store configuration information from a legacy security system, in accord with embodiments of the present invention. An initial step involves the coupling of the SMA controller to a keypad bus of the legacy security system (710). FIGS. 6A and 6B illustrate examples of coupling configurations through which SMA controller 120 can communicate with an alarm processor 520 of the legacy security system. Once the SMA controller is coupled to the keypad bus, the SMA controller can determine the serial digital protocol used by the legacy security system to which the SMA controller has been coupled (720). In one embodiment of the present invention, determination of the type of serial digital protocol can be performed passively by analyzing communications between alarm processor 520 and keypad processor 575. SMA controller 120 can compare the serial digital protocol communication signals with a variety of serial digital protocols stored in the SMA controller. Alternatively, SMA controller 120 can actively determine the type of legacy security system by transmitting a variety of serial digital protocol commands onto the keypad bus (i.e., emulating a keypad) until a response from the legacy security system is received. Once the serial digital protocol is determined, the SMA controller will store an identifier of the serial digital protocol and will use the identified serial digital protocol in communications with the legacy security system and that information is stored in the SMA controller.

The SMA controller can then transmit one or more commands to extract configuration information from the legacy security system (730). The commands used to extract the configuration information are the same as those that could be provided by keypad entries on keypad 570. SMA controller 120 provides the keypad commands automatically to alarm processor 520 and receives the responsive configuration codes over the keypad bus. This transfer of information can be performed without user interaction, thereby reducing or eliminating the need for an installation technician to know, or have access to, keypad sequences for one or more types of legacy security systems. The types of configuration information requested by the SMA controller can be, for example, sensor identification, sensor type, and zone configuration of the legacy security system. Configuration information can include information regarding all sensors coupled to the legacy security system, both hardwired and RF sensors.

As the configuration information is received by SMA controller 120, the SMA controller can store the configuration information in the SMA controller (e.g., in memory 260). The SMA controller can also provide the configuration information to a database server 185 in operator domain 160 for storage and modification.

Once the legacy sensor configuration information is stored in the SMA controller or the SMA controller and a database server, a user can edit that configuration information either on the SMA controller or remotely by accessing portal server 170 (750). For example, the SMA controller can provide configuration information related to all the legacy sensors on a coupled touch screen display. A user can then edit that information to provide meaningful specifics as to the physical location of the sensor or zone within the home domain or other characteristics related to the sensor. The SMA controller can provide interactive displays for the user to define or edit information related to the sensors and zones extracted from the legacy security system. The edited information is stored in a local memory of the SMA controller and also transmitted for storage in a server in the operator domain. Through the editing process, to the extent that information extracted from the legacy security system is cryptic or not self explanatory, a user can provide names and other identifiers of sensors and zones for ease of understanding events reported by the SMA controller. As configuration information is received from the legacy security system, the SMA controller will match that information (e.g., zone functions) with common-language equivalents, as configured.

In addition to security sensors coupled to a legacy security system, SMA controller 120 can also directly receive and interpret signals from a variety of RF sensors (e.g., RF sensors 130). The SMA controller can be configured with information related to those RF sensors, including zone information, during an installation process (760). Such a configuration of an SMA controller to receive and interpret RF sensor information is described in co-pending U.S. patent application Ser. No. 12/568,718, filed on Sep. 29, 2009, entitled “Configurable Controller and Interface for Home SMA, Phone and Multimedia,” naming Alan Wade Cohn, Gary Robert Faulkner, James A. Johnson, James Edward Kitchen, David Leon Proft, and Corey Wayne Quain as inventors, which is incorporated for all that it teaches. Additionally, the SMA controller can also be configured to communicate with and control monitoring devices (e.g., monitoring devices 140) and home area network devices having an automation interface (e.g., home automation devices 145). A description of such a configuration is also provided in the above-referenced co-pending patent application.

Once configured, the SMA controller takes over responsibility for receiving, interpreting, and transmitting sensor state change information for all sensors coupled to the SMA controller, including those sensors coupled to the legacy security system. The legacy security system is therefore disarmed (770). Typically, the legacy security system is disarmed prior to installation of the SMA controller. Disarming the legacy security system can include decoupling the legacy security system from PSTN 550, thereby disabling the legacy security system from communicating directly with a central monitoring service system 560. Once disarmed, the legacy security system merely is a conduit through which sensor state information from sensors 530 can be provided to SMA controller 120. The legacy security system is a slave to the SMA controller. In order for alarm events to be transmitted to a central station 190, a user will arm SMA controller 120 (780). In this manner, all communications are handled by SMA controller 120 over access domain 150 to operator domain 160. The armed or disarmed state of the SMA controller determines, in part, the types of information related to a sensor state change communicated to central station 190.

FIG. 8 is a simplified flow diagram illustrating a process performed in response to a legacy sensor state change, in accord with embodiments of the present invention. In response to a state change of a legacy security system sensor 530 (810), SMA controller 120 receives a signal on keypad bus 590 from legacy security processor 520 (820). Such information can include, for example, an identifier of the sensor experiencing a state change in the protocol of the legacy security system. The SMA controller will interpret the received signal in light of the stored sensor and zone information related to the legacy security system's sensors (830). Such an interpretation can be performed, for example, by comparing the received legacy security system identifier with stored SMA controller identifiers for those sensors through an appropriate mapping.

Once interpreted, the SMA controller can display the event information on a coupled screen. SMA controller 120 can also provide the event information to a remote server 165 in operator domain 160 for further action such as display to a remote user or, if the SMA controller is armed, relay to a central station 190. In addition, the SMA controller can sound an alarm in response to the sensor state change, if armed.

In an alternative embodiment, legacy security controller unit 510 can be removed after providing configuration information to SMA controller 120. For example, the SMA controller can be configured, through the use of an appropriate communication module (e.g., coupled to SPI interface 250), to communicate directly with RF sensors that originally communicated with the legacy security controller. In another example, the hard wired sensors of the legacy security system can be decoupled from the legacy security controller unit and coupled to a unit configured to communicate sensor state change information directly to the SMA controller (e.g., a daughter card).

As discussed above, embodiments of the SMA controller 120 can be configured to monitor and control a variety of security sensors, cameras and automation devices. Embodiments of SMA controller 120 can be further configured to provide an installer-intuitive, guided activation and provisioning mechanism for installation of the SMA controller. One example of such an activation and provisioning mechanism is described in co-pending U.S. application Ser. No. 12/691,992, filed on Jan. 22, 2010, entitled “Method, System and Apparatus for Activation of a Home Security, Monitoring and Automation Controller,” naming Alan Wade Cohn, Gary Robert Faulkner, James A. Johnson, James Edward Kitchen, David Leon Proft, and Corey Wayne Quain as inventors, which is incorporated for all that it discloses. Through the use of a guided activation and provisioning mechanism, embodiments of the SMA controller do not require specialized technicians to perform such an installation. Instead, embodiments of the SMA controller are provided with an extensible software-based architecture for an activation work flow that guides the end-user or installer through each step of the activation process and which performs various network and sensor configuration tasks unseen to the person conducting the activation process and without need for user interaction. As an example, the tasks involved in gathering the configuration information from the legacy security system involve a series of keypad bus commands sent to the legacy security system by the SMA controller. The activation and provisioning process will perform these tasks automatically and without need of human interaction.

The activation/provisioning workflow described above is designed to be performed entirely using SMA controller 120 without the use of any external computing resources or input device beyond a touch screen display associated with the SMA controller and any updates provided by a remote server. Displayed instructions and input screens are incorporated with the software (e.g., firmware) of the SMA controller such that a non-technical end-user or an installation technician without specialized training can perform an install of the SMA controller, along with the associated security sensors, camera monitoring devices, and network routing devices. In addition, since much of the network configuration is performed automatically by the SMA controller, the amount of typing of keypad sequences and other information, and hence the opportunity for errors in such typing, is dramatically reduced. Since the installation process is performed using only a display coupled to the SMA controller, the need for additional equipment, such as a computer to perform the installation, is eliminated, and thereby the cost of performing installations is also reduced. Further, the elimination of lengthy typing of keypad sequences and the like, results in a faster installation process with less frustration than is found for typical systems. Thus, if a technician is performing such an installation, the cost for each installation is reduced due to the reduction in the need for installation technician time. Persons of ordinary skill in the art will understand that all of these factors provide advantages to systems embodying the present invention over traditional systems that require additional equipment to perform installations and specialized technician training, thereby increasing the costs for performing such installations.

An Example Computing and Network Environment

As shown above, the present invention can be implemented using a variety of computer systems and networks. An example of one such computing and network environment is described below with reference to FIGS. 9 and 10.

FIG. 9 depicts a block diagram of a computer system 910 suitable for implementing aspects of the present invention (e.g., servers 165, portal server 170, backup server 175, telephony server 180, and database server 185). Computer system 910 includes a bus 912 which interconnects major subsystems of computer system 910, such as a central processor 914, a system memory 917 (typically RAM, but which may also include ROM, flash RAM, or the like), an input/output controller 918, an external audio device, such as a speaker system 920 via an audio output interface 922, an external device, such as a display screen 924 via display adapter 926, serial ports 928 and 930, a keyboard 932 (interfaced with a keyboard controller 933), a storage interface 934, a floppy disk drive 937 operative to receive a floppy disk 938, a host bus adapter (HBA) interface card 935A operative to connect with a Fibre Channel network 990, a host bus adapter (HBA) interface card 935B operative to connect to a SCSI bus 939, and an optical disk drive 940 operative to receive an optical disk 942. Also included are a mouse 946 (or other point-and-click device, coupled to bus 912 via serial port 928), a modem 947 (coupled to bus 912 via serial port 930), and a network interface 948 (coupled directly to bus 912).

Bus 912 allows data communication between central processor 914 and system memory 917, which may include read-only memory (ROM) or flash memory (neither shown), and random access memory (RAM) (not shown), as previously noted. The RAM is generally the main memory into which the operating system and application programs are loaded. The ROM or flash memory can contain, among other code, the Basic Input-Output system (BIOS) which controls basic hardware operation such as the interaction with peripheral components. Applications resident with computer system 910 are generally stored on and accessed via a computer-readable medium, such as a hard disk drive (e.g., fixed disk 944), an optical drive (e.g., optical drive 940), a floppy disk unit 937, or other storage medium. Additionally, applications can be in the form of electronic signals modulated in accordance with the application and data communication technology when accessed via network modem 947 or interface 948.

Storage interface 934, as with the other storage interfaces of computer system 910, can connect to a standard computer-readable medium for storage and/or retrieval of information, such as a fixed disk drive 944. Fixed disk drive 944 may be a part of computer system 910 or may be separate and accessed through other interface systems. Modem 947 may provide a direct connection to a remote server via a telephone link or to the Internet via an internet service provider (ISP). Network interface 948 may provide a direct connection to a remote server via a direct network link to the Internet via a POP (point of presence). Network interface 948 may provide such connection using wireless techniques, including digital cellular telephone connection, Cellular Digital Packet Data (CDPD) connection, digital satellite data connection or the like.

Many other devices or subsystems (not shown) may be connected in a similar manner (e.g., document scanners, digital cameras and so on). Conversely, all of the devices shown in FIG. 9 need not be present to practice the present invention. The devices and subsystems can be interconnected in different ways from that shown in FIG. 9. The operation of a computer system such as that shown in FIG. 9 is readily known in the art and is not discussed in detail in this application. Code to implement the present invention can be stored in computer-readable storage media such as one or more of system memory 917, fixed disk 944, optical disk 942, or floppy disk 938. The operating system provided on computer system 910 may be MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, Linux®, or another known operating system.

Moreover, regarding the signals described herein, those skilled in the art will recognize that a signal can be directly transmitted from a first block to a second block, or a signal can be modified (e.g., amplified, attenuated, delayed, latched, buffered, inverted, filtered, or otherwise modified) between the blocks. Although the signals of the above described embodiment are characterized as transmitted from one block to the next, other embodiments of the present invention may include modified signals in place of such directly transmitted signals as long as the informational and/or functional aspect of the signal is transmitted between blocks. To some extent, a signal input at a second block can be conceptualized as a second signal derived from a first signal output from a first block due to physical limitations of the circuitry involved (e.g., there will inevitably be some attenuation and delay). Therefore, as used herein, a second signal derived from a first signal includes the first signal or any modifications to the first signal, whether due to circuit limitations or due to passage through other circuit elements which do not change the informational and/or final functional aspect of the first signal.

FIG. 10 is a block diagram depicting a network architecture 1000 in which client systems 1010, 1020 and 1030, as well as storage servers 1040A and 1040B (any of which can be implemented using computer system 910), are coupled to a network 1050. Storage server 1040A is further depicted as having storage devices 1060A(1)-(N) directly attached, and storage server 1040B is depicted with storage devices 1060B(1)-(N) directly attached. Storage servers 1040A and 1040B are also connected to a SAN fabric 1070, although connection to a storage area network is not required for operation of the invention. SAN fabric 1070 supports access to storage devices 1080(1)-(N) by storage servers 1040A and 1040B, and so by client systems 1010, 1020 and 1030 via network 1050. Intelligent storage array 1090 is also shown as an example of a specific storage device accessible via SAN fabric 1070.

With reference to computer system 910, modem 947, network interface 948 or some other method can be used to provide connectivity from each of client computer systems 1010, 1020 and 1030 to network 1050. Client systems 1010, 1020 and 1030 are able to access information on storage server 1040A or 1040B using, for example, a web browser or other client software (not shown). Such a client allows client systems 1010, 1020 and 1030 to access data hosted by storage server 1040A or 1040B or one of storage devices 1060A(1)-(N), 1060B(1)-(N), 1080(1)-(N) or intelligent storage array 1090. FIG. 10 depicts the use of a network such as the Internet for exchanging data, but the present invention is not limited to the Internet or any particular network-based environment.

Other Embodiments

The present invention is well adapted to attain the advantages mentioned as well as others inherent therein. While the present invention has been depicted, described, and is defined by reference to particular embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alteration, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts. The depicted and described embodiments are examples only, and are not exhaustive of the scope of the invention.

The foregoing describes embodiments including components contained within other components (e.g., the various elements shown as components of computer system 910). Such architectures are merely examples, and, in fact, many other architectures can be implemented which achieve the same functionality. In an abstract but still definite sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermediate components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality.

The foregoing detailed description has set forth various embodiments of the present invention via the use of block diagrams, flowcharts, and examples. It will be understood by those within the art that each block diagram component, flowchart step, operation and/or component illustrated by the use of examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof. For example, specific electronic components can be employed in an application specific integrated circuit or similar or related circuitry for implementing the functions associated with one or more of the described functional blocks.

The present invention has been described in the context of fully functional computer systems; however, those skilled in the art will appreciate that the present invention is capable of being distributed as a program product in a variety of forms, and that the present invention applies equally regardless of the particular type of computer-readable media used to actually carry out the distribution. Examples of computer-readable media include computer-readable storage media, as well as media storage and distribution systems developed in the future.

The above-discussed embodiments can be implemented by software modules that perform one or more tasks associated with the embodiments. The software modules discussed herein may include script, batch, or other executable files. The software modules may be stored on a machine-readable or computer-readable storage media such as magnetic floppy disks, hard disks, semiconductor memory (e.g., RAM, ROM, and flash-type media), optical discs (e.g., CD-ROMs, CD-Rs, and DVDs), or other types of memory modules. A storage device used for storing firmware or hardware modules in accordance with an embodiment of the invention can also include a semiconductor-based memory, which may be permanently, removably or remotely coupled to a microprocessor/memory system. Thus, the modules can be stored within a computer system memory to configure the computer system to perform the functions of the module. Other new and various types of computer-readable storage media may be used to store the modules discussed herein.

The above description is intended to be illustrative of the invention and should not be taken to be limiting. Other embodiments within the scope of the present invention are possible. Those skilled in the art will readily implement the steps necessary to provide the structures and the methods disclosed herein, and will understand that the process parameters and sequence of steps are given by way of example only and can be varied to achieve the desired structure as well as modifications that are within the scope of the invention. Variations and modifications of the embodiments disclosed herein can be made based on the description set forth herein, without departing from the scope of the invention.

Consequently, the invention is intended to be limited only by the scope of the appended claims, giving full cognizance to equivalents in all respects. 

What is claimed is:
 1. A method comprising: transmitting, by a controller, to a security system, and via a plurality of protocols, a plurality of probe messages; receiving, by the controller, from the security system, and via a protocol of the plurality of protocols, a response to at least one probe message of the plurality of probe messages, wherein two or more components of the security system are configured to communicate via the protocol; receiving, by the controller and via the protocol, configuration information associated with the security system; receiving, by the controller, from the security system, and via the protocol, a sensor signal indicating a status of a sensor of the security system; determining, based on the configuration information and the sensor signal, an interpreted sensor message; and transmitting, by the controller and based on the configuration information, an alarm message indicating the interpreted sensor message.
 2. The method of claim 1, wherein the protocol is for communication via a wired communication medium.
 3. The method of claim 1, wherein the protocol is for communication via a wireless communication medium.
 4. The method of claim 1, further comprising: transmitting, by the controller, to the security system, and via the protocol, a request message comprising a request for the configuration information.
 5. The method of claim 1, wherein the at least one probe message of the plurality of probe messages comprises at least one of a control command for the security system, security system arm/disarm information, zone sensor trip information, sensor state information, or a security system arming code.
 6. The method of claim 1, further comprising: displaying, on a display configured to communicate with the controller, information indicating the interpreted sensor message.
 7. The method of claim 1, further comprising: determining, based on the configuration information and via an input device configured to communicate with the controller, modified configuration information; and transmitting, to a server and by the controller, the modified configuration information, wherein the server stores the configuration information.
 8. The method of claim 1, further comprising: transmitting, by the controller and to a server, the configuration information; and receiving, by the controller and from the server, modified configuration information, wherein the modified configuration information is determined, based on the configuration information, by a user of the server.
 9. The method of claim 1, wherein the transmitting the alarm message comprises transmitting the alarm message to a computing device selected, based on the configuration information, from at least one of: a server located external to a premises of the controller, or a device located at the premises of the controller and comprising a display.
 10. The method of claim 1, wherein: the controller is configured to operate in a mode comprising one of an armed mode or a disarmed mode, and the transmitting the alarm message comprises transmitting the alarm message to a computing device selected, based on the mode in which the controller is configured to operate, from at least one of: a server located external to a premises of the controller, or a device located at the premises and comprising a display.
 11. The method of claim 1, where the protocol comprises a serial digital protocol.
 12. The method of claim 1, wherein the sensor of the security system comprises one or more of a door sensor, a window sensor, a point of entry sensor, a motion sensor, a smoke detector, a heat sensor, a fire sensor, an automation device, a still-image camera, a video camera, a glass break detector, an inertial detector, a water detector, a carbon dioxide detector, or a key fob device.
 13. A device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the device to: transmit, to a security system and via a plurality of protocols, a plurality of probe messages; receive, from the security system and via a protocol of the plurality of protocols, a response to at least one probe message of the plurality of probe messages, wherein two or more components of the security system are configured to communicate via the protocol; receive, via the protocol, configuration information associated with the security system; receive, from the security system and via the protocol, a sensor signal indicating a status of a sensor of the security system; determine, based on the configuration information and the sensor signal, an interpreted sensor message; and transmit, based on the configuration information, an alarm message indicating the interpreted sensor message.
 14. The device of claim 13, wherein the instructions, when executed by the one or more processors, further cause the device to: determine, based on the configuration information and via an input device in configured to communicate with the device, modified configuration information; and transmit the modified configuration information to a server, wherein the server stores the modified configuration information.
 15. The device of claim 13, wherein the instructions, when executed by the one or more processors, further cause the device to: transmit, to a server, the configuration information; and receive, from the server, modified configuration information, wherein the modified configuration information is determined, based on the configuration information, by a user of the server.
 16. The device of claim 13, wherein the instructions, when executed by the one or more processors, further cause the device to: transmit the alarm message to a computing device selected, based on the configuration information, from at least one of: a server located external to a premises of the device, or a second device comprising a display and located at the premises of the device.
 17. The device of claim 13, wherein the device is configured to operate in a mode comprising one of an armed mode or a disarmed mode, and the instructions, when executed by the one or more processors, further cause the device to: transmit the alarm message to a computing device selected, based on the mode in which the device is configured to operate, from at least one of: a server located external to a premises of the device, or a second device comprising a display and located at the premises of the device.
 18. The device of claim 13, wherein the instructions, when executed by the one or more processors, further cause the device to: transmit, to the security system and via the protocol, a request message, wherein the request message comprises a request for the configuration information.
 19. The device of claim 13, wherein the configuration information comprises at least one of a sensor identifier of the sensor, a sensor type of the sensor, or a zone indicator associated with the sensor.
 20. The device of claim 13, wherein the instructions, when executed by the one or more processors, further cause the device to: transmit the plurality of probe messages to a controller of the security system.
 21. A method comprising: transmitting, by a controller, to a security system, and via a plurality of protocols, a plurality of probe messages; receiving, by the controller, from the security system, and via a protocol of the plurality of protocols, a response to at least one probe message of the plurality of probe messages, wherein two or more components of the security system are configured to communicate via the protocol; receiving, by the controller and via the protocol, configuration information associated with the security system; receiving, by the controller, from the security system, and via the protocol, a sensor signal indicating a status of a sensor of the security system; and transmitting, by the controller and based on the configuration information, an alarm message indicating the status of the sensor.
 22. The method of claim 21, further comprising: determining, based on the configuration information, a computing device; and transmitting the alarm message to the computing device.
 23. The method of claim 22, wherein the computing device comprises at least one of: a server located external to a premises of the controller, or a device located at the premises of the controller and comprising a display.
 24. The method of claim 21, further comprising: transmitting, by the controller, to the security system, and via the protocol, a request message; and wherein the receiving the configuration information comprises: receiving, based on the transmitting the request message, the configuration information.
 25. The method of claim 24, wherein: the security system comprises a security system controller, the transmitting the request message comprises transmitting the request message to the security system controller, and the receiving the configuration information comprises receiving the configuration information from the security system controller.
 26. The method of claim 24, wherein: the security system comprises a security system controller and a keypad device, wherein the keypad device is configured to communicate with, via the protocol, the security system controller, and transmit a configuration information request command to the security system controller, the security system controller is configured to transmit, based on the receiving the configuration information request command and to a source of the configuration information request command, the configuration information, and the request message transmitted to the security system controller by the controller comprises the configuration information request command. 